Community management refers to the process of defining, organizing, and moderating portals that contain a file repository, blogs, discussion forums, or collaborative workspaces like wikis. Community management comprises the following activities:
■ Defining communities and their resource libraries, blogs, discussion forums, or wikis
■ Defining community display, navigation, and structure
■ Moderating membership and conversations
■ Defining notifications
■ Defining security and access
■ Managing document attachments
Who depends on this?
Your community management activities must be completed before members can view or post to forums, blogs, resource libraries, or wikis.
What must be done before you can start?
■ You cannot perform some community management tasks until after a Community has been created in iMIS.
Putting it all together
Community management comprises two general workflows:
■ The process of defining communities entails the following actions, which must be performed in the order shown:
1. Define a community. By default, a Community contains iParts that enable addition of forums, blogs, wikis, announcements, and items in a resource library.
2. Define the layout of the community's parts.
3. Define notifications for the community.
4. Manage the community roster and subscriptions.
5. (optional) Manage limitations and definitions for file attachments.
■ The process of community maintenance entails the following actions, performed as needed:
□ Manage security.
□ Moderate conversations.
□ Troubleshoot communities.
Types of user privileges
There are three system-defined security groups that affect user privileges relevant to managing communities.
□ Content Administrator: member of a MasterAdmin Content Authority Group (CAG).
□ Community User: A user who views or contributes to or authors community documents such as blogs, libraries, or forums, and may own a community document.
□ Community Administrator: A user with the ability to set up communities and edit Community permissions. Belonging to this security group gives the user the ability to edit or delete community documents, regardless of the document's owner.